According to @Tetranode, Vitalik Buterin says Ethereum’s combination of PeerDAS on mainnet and ZK-EVMs at alpha with production-quality performance means the scalability trilemma is solved with live running code, while safety work remains for ZK-EVMs; he expects small portions of the network to use ZK-EVMs in 2026. Source: x.com/VitalikButerin/status/2007559523528233041; x.com/Tetranode/status/2007613446616231952. Vitalik states PeerDAS is already live on mainnet and ZK-EVMs are production-quality on performance today, with the trilemma solution emerging from these components; he frames this as a fundamental shift to a decentralized, consensus-enabled, high-bandwidth network. Source: x.com/VitalikButerin/status/2007559523528233041. He outlines a rollout timeline: in 2026, non-ZK-EVM-dependent gas limit increases driven by BALs and ePBS with first opportunities to run a ZK-EVM node; in 2026–28, gas repricings, state structure changes, and execution payload moving into blobs; in 2027–30, further large gas limit increases as ZK-EVMs become the primary way to validate blocks. Source: x.com/VitalikButerin/status/2007559523528233041. For context, he contrasts previous p2p paradigms—BitTorrent (high bandwidth, decentralized, no consensus) and Bitcoin (decentralized with consensus but low bandwidth due to replication)—with Ethereum’s intended decentralized, consensus, high-bandwidth design under PeerDAS and ZK-EVMs. Source: x.com/VitalikButerin/status/2007559523528233041. Vitalik also highlights distributed block building, aiming to minimize centralized interference in transaction inclusion and improve geographical fairness through in-protocol or marketplace-based mechanisms. Source: x.com/VitalikButerin/status/2007559523528233041. He notes this was a 10-year journey starting from early DAS research and links the first commit of his data availability and erasure coding note. Source: github.com/ethereum/research/wiki/A-note-on-data-availability-and-erasure-coding/52e1d03b0254cded8b67105be17ba9890b7ad8d3; x.com/VitalikButerin/status/2007559523528233041.